@dafyre said in Normal Forms of Systems Administration:

@scottalanmiller said in Normal Forms of Systems Administration:

@Tim_G said in Normal Forms of Systems Administration:

So if 4th is strictly using RSAT... would 5th be full automation using SCCM, SCVMM, Orchestrator, and App Controller?

Yes, I believe so. Those would be tools in the Microsoft toolset for that. They tend to take a very different approach than many of their competitors and it's been a while since I've used it. Not sure if SCCM goes all of the way to defined state or just really heavily automated forth form. But I think you can get to that state.

I believe it is properly state defined (fifth form) but not code defined like most of the alternatives.

I think I got lost in all the clutter... but why do you separate Remote GUI from Remote CLI ?

Essentially "automatable interface" vs non-automatable interface. Not that GUIs cannot be automated, but effectively they cannot be.

It's true that you can make stateless systems without DevOps tooling and approaches. But the nature and assumptions of those systems is that you cannot. Just letting arbitrary logins (even of administrators) can undermine that. One of the beauties of the pure DevOps model is the lack of logins. Much like functional programming.

Fixed

@JJoyner1985 said in UNIX: What Is a Tarball:

So, do you think the reason I am seeing a lot more gzip in use with tarballs is due to the familiarity of gzip and the negligible difference in the compression between it and bzip2? Basically, bzip2 doesn't make enough of an improvement with sufficient regularity to entice people to move away from gzip, or is there some other benefit to gzip that my training material hasn't covered?

That's correct. The difference between the two is generally small enough that people are not concerned. And lots of systems still don't have bzip2 installed by default so if you want scripts or whatever to work universally you often use gzip because you know that it is always there and predictable.

http://blog.takipi.com/deployment-management-tools-chef-vs-puppet-vs-ansible-vs-saltstack-vs-fabric/

Very interesting, will check that out.

@techgameteddy said in Looking to Move from Windows to Linux Administration:

@scottalanmiller To obtain the RHCSE you need to get the RHCSA first dont you? Should I focus on getting those at all then? Im definitely going to create a Media Server this weekend and a wordpress server at home. This is good information. Im also going to look into Containers too. I have noticed that its become a hot topic these days.

The RHCE does seem to bring in job options. But certs, in general, are not a path to Linux jobs. I would focus more on gaining skills and experience. Volunteer work can do wonders for getting into Linux.

In larger teams, you normally have 24x7 staff. So the reboot schedule goes to the current shift to monitor. It's only shops that lack round the clock scheduling that have this as a real issue, and if you don't have 24x7, shouldn't you be outsourcing to a shop that does if you really need that at all? I think that this normally (maybe not always) becomes a problem when you are dealing with layers and layers of other problems like not having enough IT staff to properly staff a department without causing unnecessary cost and risk and choosing not to outsource to an MSP/ITSP that could do this cost effectively.

@scottalanmiller Thanks. I got it. I overthink everything. 🙂

User of CentOS and Ubuntu servers myself. Mint is still top go-to for desktop, though there are interesting alternatives like ElementaryOS.

Linux is not always easy to learn, I just forget everything if it's not regularly used, especially CLI with their bazillion switches that no mere mortal can ever memorize. And moving between different distros where commands don't work exactly the same, Aptitude and Yum, etc.

Cool, but always challenging.

@DustinB3403 said in Linux: Checking Filesystem Usage with df:

Will there be a topic on "managing inode in linux"

Yes, but it is going to go into an "Advanced Topics" section. Just as LVM and MD will have high level "normal" admin sections and eventually delve much deeper in advanced sections. I want to cover everything in a "normal admin" capacity like you would learn from the RHCE up front. Then go back and cover the nitty gritty details that other admin books don't. So it will basically take two passes but the hope is that the first pass will take you from "starting point" to "competent Linux Admin" then the second part will go where normal admin guides don't tread.

@tonyshowoff said in Linux: Zip and 7Zip:

Sorry if this was mentioned but I didn't see it directly mentioned for clarity:

If your compression is unavailable directly in tar (-J being essentially 7zip, my favourite), you can tar it first (without compression) and then compress the tar, this maintains both Unix metadata and also gives the benefit.

Also, if you compress something already compressed you won't get the best benefit, at least not when it comes to using something as powerful as LZMA/7zip.

I believe that that is mentioned in the tar article.

It doesn't update as "new" when I just update the list. Only if I comment on the thread.

@Dashrender said in From Windows to UNIX: Monolithic to Modular Design:

I suppose it's less of an issue as well, since Linux Distros are free, you just have another VM running the other software.
Windows, you'd have the Windows tax.

Exactly. A VM or a container or an application jail. Lots of options for mediation if you want the conflicting packages.

@scottalanmiller I have avoided bad updates by waiting a week or two and googling the updates that show in my WSUS. If I worked with a team of people who only did help desk, I would be more willing to take the leap. That being said, I do have critical updates set to automatically download and install for all clients. Servers I do regularly and manually. Critical updates appear less often and are fewer in numbers compared with other updates that seem to cause the problems.

It's not bad, I use one liners all the time, and that's a very simple one liner. Linux culture is to use a string of separate commands instead of one that does everything.